<?php
/**
 * <https://y.st./>
 * Copyright © 2019 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'Firstborn',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2019/05/10.jpg" alt="Purple flowers" class="framed-centred-image" width="800" height="480"/>
<section id="diet">
	<h2>Dietary intake</h2>
	<p>
		I didn&apos;t feel well today.
		I went to bed with a terrible neck ache, likely from all the stuff I had to carry around in Eugene.
		If I&apos;d just went home after the dietary meeting like I didn&apos;t want to do and dropped off what I no longer needed before heading back to Eugene for the $a[EUGLUG] meeting, I probably would have been fine.
		And that neck ache progressed to include a headache.
		I also overexerted myself again riding around when I should have conserved my strength.
		I ended up getting sick again today.
		I planned 372 grams of leftover stew for dinner, but otherwise, was feeling too unwell to do meals at all.
		I slowly ate 393 grams of pretzels and 472 grams of my mixed juice though, so I was by no means going hungry.
	</p>
</section>
<section id="drudgery">
	<h2>Drudgery</h2>
	<p>
		My discussion post for the day:
	</p>
	<blockquote>
		<h3>10-tape rotation</h3>
		<p>
			The advantage of the ten-tape rotation is that if you have a five-day work week, you keep two weeks&apos; worth of backup data at all times.
			You have one full backup per week, plus four incremental backups.
			The book recommends that the full backup take place on Friday (Stanek, 1999), which seems like a sensible choice if your company is one that works Monday through Friday.
			That way, you&apos;re not waiting two days to back up data that isn&apos;t changing in the mean time.
			I&apos;ve seen a few companies with other business days though, such as Tuesday through Saturday.
			For those companies, backing up on Saturday would be a better idea.
			With the 10-tape backup plan, you also need fewer tapes than other recommended methods, meaning you have a reduced cost.
			However, that does come at a cost: you don&apos;t have as much backed up.
			You&apos;ve only got two weeks&apos; worth of backup data, and if your company is open every day, you&apos;re not getting the daily backup s that would probably be wise to have.
		</p>
		<h3>15-tape rotation</h3>
		<p>
			Another option presented by the reading material this week is the 15-tape backup plan.
			Using this method, you have three weeks&apos; worth of backup data instead of two.
			Even better, one set can be rotated to off-site storage each week (Stanek, 1999).
			My guess is that the oldest of the two not being overwritten this week goes off-site, but if something happens to your on-site backups, you lose no more than two weeks&apos; worth of data.
			(The newest copy is on-site, the oldest copy is on-site being overwritten, and the middle copy is safely off-site.)
			You could instead rotate the newest backups off-site, so if something happens to your on-site location, no more than one week&apos;s worth of data is lost.
			I guess the main disadvantage of this plan is that it again doesn&apos;t account for seven-day work weeks.
			It&apos;s also a little extra effort, as rotating the backups off-site is an added task that mush be completed each week.
		</p>
		<h3>14-tape rotation</h3>
		<p>
			The 14-tape rotation finally accounts for seven-day work weeks.
			A full backup is made every week, and an incremental backup made each day in which the full backup doesn&apos;t take place.
			The main disadvantages of this plan are that we&apos;ve lost the advantages of the 15-tape rotation.
			Specifically, we&apos;re back to having no off-site backup and we&apos;re back to having only two weeks&apos; worth of backup data.
			That is to say, the 14-tape backup plan has the same disadvantages as the 10-day backup plan, with the exception that we&apos;re accounting for seven-day work weeks.
			The chapter recommends scheduling full backups on Sundays (Stanek, 1999), but what day is best probably depends on your business flow.
			My guess is that the idea is that Sunday is a slow day for many businesses, and that it comes right after Saturday, in which you got a lot done.
			If your business is different, you might have a different busy day followed by a slow day, and should probably schedule the full backup for that slow day.
			That way, the work done on the busy day is captured in the backup, but business is slow enough that backing up data doesn&apos;t interfere with ongoing work as much.
		</p>
		<p>
			Though not mentioned by the textbook, it&apos;s worth noting that for dealing with the lack of an off-site backup and lack of a third week of backup data, we could theorise a hypothetical 21-tape rotation plan ...
			The disadvantage of course would be that we&apos;d need to buy even more tapes, which is an added expense.
		</p>
		<div class="APA_references">
			<h3>References:</h3>
			<p>
				Stanek, W. R. (1999). <a href="https://my.uopeople.edu/pluginfile.php/476020/mod_book/chapter/187042/MSDataBackupRec.pdf">Chapter 14: Data Backup and Recovery</a>. Retrieved from <code>https://my.uopeople.edu/pluginfile.php/476020/mod_book/chapter/187042/MSDataBackupRec.pdf</code>
			</p>
		</div>
	</blockquote>
</section>
<section id="names">
	<h2>Names</h2>
	<p>
		I didn&apos;t hear it myself, but apparently, the head manager was asking a bunch of the other employees how much money it would take to get them to name their firstborn child &quot;Adolf Hitler&quot;.
		What a bizarre thing to ask.
	</p>
	<p>
		As I said, they didn&apos;t ask me, but if they had, I don&apos;t think the answer would be what they&apos;d expect.
		The problem isn&apos;t the name, although the name is problematic.
		The problem is the child.
		No amount of money could ever get me to create a child, so I could never have a firstborn to name.
		Then again, maybe they didn&apos;t ask me because they know I&apos;m planning to never create more people.
		I&apos;m not exactly quiet about that fact.
	</p>
</section>
END
);
